home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
- USERSETUP(UNIX) 3/14/79 USERSETUP(UNIX)
-
-
-
- NAME
- usersetup - setup users file
-
- SYNOPSIS
- .../_b_i_n/_u_s_e_r_s_e_t_u_p [ flags [ pathname ] ]
-
- DESCRIPTION
- The /_e_t_c/_p_a_s_s_w_d file is read and reformatted to become the
- INGRES users file, stored into .../_f_i_l_e_s/_u_s_e_r_s. If _p_a_t_h_n_a_m_e
- is specified, it replaces ``...''. If pathname is ``-'',
- the result is written to the standard output.
-
- The user name, user, and group id's are initialized to be
- identical to the corresponding entry in the /_e_t_c/_p_a_s_s_w_d
- file. The status field is initialized to be 000001, except
- for user _i_n_g_r_e_s, which is initialized to all permission bits
- set. If the _s_t_a_t_u_s parameter is provided, the field is set
- to this instead. The ``initialization file'' parameter is
- set to the file ._i_n_g_r_e_s in the user's login directory. The
- user code field is initialized with sequential two-character
- codes. All other fields are initialized to be null.
-
- After running _u_s_e_r_s_e_t_u_p, the _u_s_e_r_s file must be edited. Any
- users who are to have any special authorizations should have
- the status field changed, according to the specifications in
- users(files). To disable a user from executing INGRES en-
- tirely, completely remove her line from the users file.
-
- As UNIX users are added or deleted from the /_e_t_c/_p_a_s_s_w_d
- file, the _u_s_e_r_s file will need to be editted to reflect the
- changes. For deleted users, it is only necessary to delete
- the line for that user from the _u_s_e_r_s file. To add a user,
- you must assign that user a code in the form "aa" and enter
- a line in the users file in the form:
- name:cc:uid:gid:status:flags:proctab:initfile::databases
- where _n_a_m_e is the user name (taken from the first field of
- the /_e_t_c/_p_a_s_s_w_d file entry for this user), _c_c is the user
- code assigned, which must be exactly two characters long and
- must not be the same as any other existing user codes, _u_i_d
- and _g_i_d are the user and group ids (taken from the third and
- fourth fields in the /_e_t_c/_p_a_s_s_w_d entry), _s_t_a_t_u_s is the
- status bits for this user, normally 000000, _f_l_a_g_s are the
- default flags for INGRES (on a per-user basis), _p_r_o_c_t_a_b is
- the default process table for this user (which defaults to
- =_p_r_o_c_t_a_b_8), and _d_a_t_a_b_a_s_e_s is a list of the databases this
- user may enter. If null, she may use all databases. If the
- first character is a dash (``-''), the field is a comma
- separated list of databases which she may not enter. Other-
- wise, it is a list of databases which she may enter.
-
- The _d_a_t_a_b_a_s_e_s field includes the names of databases which
- may be created.
-
- _U_s_e_r_s_e_t_u_p may be executed only once, to initially create the
- _u_s_e_r_s file.
-
- FILES
- .../files/users
- /etc/passwd
-
- SEE ALSO
- ingres(unix), passwd(5), users(files)
-
- BUGS
- It should be able to bring the _u_s_e_r_s file up to date.
-
-